Configuring Direct Peering Connection
The Direct Peering connection provides the following:
| ■ | Best public routing over internet to Microsoft Cloud Services for optimal performance and reliability. |
| ■ | Ability to select the preferred Service Provider to connect to Microsoft Cloud |
| ■ | Traffic insights such as latency reporting, and prefix monitoring |
| ■ | Optimum Network Hops (AS Hops) from Microsoft Cloud |
| ■ | Route analytics and statistics - Events for Border Gateway Protocol (BGP) route anomalies (leak/hijack detection), and suboptimal routing. |
Setup Direct Peering Connection with QoS for Voice Dedicated Portal/APIs for Trunk Setup and validation :
| ■ | Establish MAPSV connection ( or between the SP DC and Azure , in case the SBCs are running hybrid) |
| ■ | Establish Express Route between the SP SIP and AC SBC on Azure |
|
Task |
Action |
System |
|---|---|---|
|
Confirm public ASN |
Register ASN. |
Peering DB |
|
Select peering locations |
Select peering locations. |
Peeringdb |
|
Associate Peer public ASN to the Azure Subscription: |
Associate peer ASN to Azure subscription using the portal - Azure | Microsoft Docs |
Azure Portal |
|
Create Direct peering connection for Peering Service** |
Guide Operator through selecting the correct sku 8075 with Voice, SKU Premium Free. |
Azure Portal |
|
Register prefixes |
Create Azure Peering Service Connection - Azure portal | Microsoft Docs |
Azure Portal |
|
Approve request |
Confirm Operator is an approved Operator Connect Operator and can generate CAS requests. |
TBD |
|
Cross Connect |
Issue Letter of Authorization (LOA) |
Cabling Team |
|
Retrieve LOA |
Retrieve LOA and order cross connect from peering location DC provider. |
Azure Portal |
|
Configure Peer(s) |
Configure BFD on second peer in each geolocation. |
SBC |
|
Confirm received routes from MSFT. |
SBC |
**If the Operator has an existing Peering connection and they either wish to use existing peering or keep existing peering and order new circuits with the same ASN, the Operator must still follow the following steps: Convert a legacy Direct peering to an Azure resource by using the Azure portal - Azure | Microsoft Docs and Enable Azure Peering Service on a Direct peering by using the Azure portal - Azure | Microsoft Docs. Note this type of request often requires manual intervention from the Azure Peering team and can take up to 3 to 4 weeks to complete.